Modular electronic display platform

ABSTRACT

Methods and systems for reconfiguring an interface device are described. The interface device may comprise a housing, one or more processors disposed in the housing, a display, a network interface that enables communication with a security system, and a module connector. One or more of a plurality of modules may be removably coupled, via the module connector, with the interface device. The plurality of modules may enable the interface device to perform different functions. An example module, when coupled to the module connector, may enable communication between multiple networks.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/952,080, filed Nov. 22, 2010, which claims the benefit of U.S. PatentApplication No. 61/263,216, filed Nov. 20, 2009, and claims the benefitof U.S. Patent Application No. 61/265,570, filed Dec. 1, 2009, and is acontinuation in part application of U.S. patent application Ser. No.11/084,232, filed Mar. 16, 2005, and is a continuation in partapplication of U.S. patent application Ser. No. 11/761,718, filed Jun.12, 2007, and is a continuation in part application of U.S. patentapplication Ser. No. 11/761,745, filed Jun. 12, 2007, and is acontinuation in part application of U.S. patent application Ser. No.12/019,554, filed Jan. 24, 2008, and is a continuation in partapplication of U.S. patent application Ser. No. 12/019,568, filed Jan.24, 2008, and is a continuation in part application of U.S. patentapplication Ser. No. 12/189,757, filed Aug. 11, 2008, and is acontinuation in part application of U.S. patent application Ser. No.12/197,895, filed Aug. 25, 2008, and is a continuation in partapplication of U.S. patent application Ser. No. 12/198,023, filed Aug.25, 2008, and is a continuation in part application of U.S. patentapplication Ser. No. 12/269,585, filed Nov. 12, 2008, and is acontinuation in part application of U.S. patent application Ser. No.12/539,537, filed Aug. 11, 2009, and is a continuation in partapplication of U.S. patent application Ser. No. 12/551,493, filed Aug.31, 2009, and is a continuation in part application of U.S. patentapplication Ser. No. 12/750,470, filed Mar. 30, 2010, and is acontinuation in part application of U.S. patent application Ser. No.12/892,801, filed Sep. 28, 2010.

TECHNICAL FIELD

This disclosure relates to consumer displays and, more particularly, toa modular touchscreen display platform that enables dynamicreconfiguration of the touchscreen with modules to provide differentfunctionality depending on current needs of the user.

BACKGROUND

Conventional consumer touchscreens, many of which are in the form ofliquid crystal display (LCD) panels, are generally designed for eithersingle task applications (e.g. picture frame) or for multi-taskapplications supported by a pre-determined and fixed hardwarecapability. For example, if the touchscreen installed in a home wasconfigured for a first type of use, and the touchscreen was subsequentlyrequired to perform a different type of use, then a new touchscreenwould be required having a different hardware function (e.g. directlymanage a heating and air-conditioning system or a security panel) thatsupported the different use type. Consequently, the conventionaltouchscreens offer an inflexible architecture for supporting newapplications as user needs change over time. Also, the conventionaltouchscreens make it relatively expensive to deploy new features due tothe hardware inflexibility. Furthermore, the conventional touchscreensmake it difficult for manufacturers or sellers of the touchscreens toaddress new applications and market trends because of the time requiredto redesign a touchscreen to support new features.

INCORPORATION BY REFERENCE

Each patent, patent application, and/or publication mentioned in thisspecification is herein incorporated by reference in its entirety to thesame extent as if each individual patent, patent application, and/orpublication was specifically and individually indicated to beincorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the integrated security system, under anembodiment.

FIG. 2 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 3 is a block diagram of the gateway software or applications, underan embodiment.

FIG. 4 is a block diagram of the gateway components, under anembodiment.

FIG. 5 is a block diagram of IP device integration with a premisenetwork, under an embodiment.

FIG. 6 is a block diagram of IP device integration with a premisenetwork, under an alternative embodiment.

FIG. 7A is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment.

FIG. 7B is a block diagram of a touchscreen 700B and module 760, underan alternative.

FIG. 7C is a block diagram of a touchscreen 700C and module 760, underanother alternative.

FIG. 7D is a block diagram of a touchscreen 700D and module 760, underanother alternative embodiment.

FIG. 7E is a block diagram of a touchscreen 700E and module 760, underyet another alternative embodiment.

FIG. 7F is a block diagram of a touchscreen 700F and module 760, understill another alternative embodiment.

FIG. 7G shows front, rear, and side views of a 4.3-inch touchscreen withmodule and a 7-inch LCD touchscreen with module, under an embodiment.

FIG. 7H shows an external module plugging into a receptacle of the7-inch touchscreen display, under an embodiment.

FIG. 7I shows an external module plugging into a receptacle of the4.3-inch touchscreen display, under an embodiment.

FIG. 7J shows the touchscreen platform positioned on a table top, underan embodiment.

FIG. 7K shows the touchscreen platform mounted on a wall, under anembodiment.

FIG. 8 is an example screenshot of a networked security touchscreen,under an embodiment.

FIG. 9 is a block diagram of network or premise device integration witha premise network, under an embodiment.

FIG. 10 is a block diagram of network or premise device integration witha premise network, under an alternative embodiment.

FIG. 11 is a flow diagram for installation of an IP device into aprivate network environment, under an embodiment.

FIG. 12 is a block diagram showing communications among IP devices ofthe private network environment, under an embodiment.

FIG. 13 is a data flow diagram for a panic alarm, under an embodiment.

FIG. 14 is a data flow diagram for device installation, under anembodiment.

FIG. 15 is a data flow diagram for a camera event, under an embodiment.

FIG. 16 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment.

FIG. 17 is a block diagram of an integrated security system wirelesslyinterfacing to proprietary security systems, under an embodiment.

FIG. 18 is a flow diagram for wirelessly ‘learning’ the gateway into anexisting security system and discovering extant sensors, under anembodiment.

DETAILED DESCRIPTION

A modular touchscreen platform is described that enables dynamicreconfiguration of the touchscreen for different functions orfunctionality. The touchscreen platform of an embodiment includes thetouchscreen display and one or more plug-in modules that each enabledifferent functions in the touchscreen platform. The modules thereforeprovide different functionality through the touchscreen depending oncurrent needs of the user. The touchscreen platform can be used as anin-home consumer touchscreen with uses including, for example, homemanagement, including energy management, security, surveillance, healthmonitoring, elder care and other consumer applications, to name a few.

Additionally, an integrated security system is described that integratesbroadband and mobile access and control with conventional securitysystems and premise devices to provide a tri-mode security network(broadband, cellular/GSM, POTS access) that enables users to remotelystay connected to their premises. The integrated security system, whiledelivering remote premise monitoring and control functionality toconventional monitored premise protection, complements existing premiseprotection equipment. The integrated security system integrates into thepremise network and couples wirelessly with the conventional securitypanel, enabling broadband access to premise security systems. Automationdevices (cameras, lamp modules, thermostats, etc.) can be added,enabling users to remotely see live video and/or pictures and controlhome devices via their personal web portal or webpage, mobile phone,and/or other remote client device. Users can also receive notificationsvia email or text message when happenings occur, or do not occur, intheir home.

Although the detailed description herein contains many specifics for thepurposes of illustration, anyone of ordinary skill in the art willappreciate that many variations and alterations to the following detailsare within the scope of the embodiments described herein. Thus, thefollowing illustrative embodiments are set forth without any loss ofgenerality to, and without imposing limitations upon, the claimedinvention.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premise security systemand a premise local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example, APIsthat allow the security system provider to integrate components of theintegrated security system into a custom call center interface. The APIsinclude XML web service APIs for integration of existing security systemprovider call center applications with the integrated security systemservice. All functionality available in the CSR Web application isprovided with these API sets. The Java and XML-based APIs of theintegrated security system support provisioning, billing, systemadministration, CSR, central station, portal user interfaces, andcontent management functions, to name a few. The integrated securitysystem can provide a customized interface to the security systemprovider's billing system, or alternatively can provide security systemdevelopers with APIs and support in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate OSS/BSSsystems of a Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured SSL sessions;USB 2.0 via ports on the gateway; 802.11b/g/n IP communications;GSM/GPRS RF WAN communications; CDMA 1×RTT RF WAN communications(optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premise and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTCP over the standard HTTP and HTTPS ports. Provided outbound TCPconnections are allowed then no special requirements on the firewallsare necessary.

FIG. 1 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, internet, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote client devices120 (e.g., PCs, mobile phones and PDAs) allowing users to remotely stayin touch with their home, business and family. In addition, thetechnology allows home security and self-monitoring information, as wellas relevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OSS/BSS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 2 is a block diagram ofcomponents of the integrated security system 100, under an embodiment.Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

-   -   Clients based on gateway client applications 202 (e.g., a        processor-based device running the gateway technology that        manages home security and automation devices).    -   A web browser 204 accessing a Web Portal application, performing        end-user configuration and customization of the integrated        security system service as well as monitoring of in-home device        status, viewing photos and video, etc. Device and user        management can also be performed by this portal application.    -   A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing        the integrated security system Mobile Portal. This type of        client 206 is used by end-users to view system status and        perform operations on devices (e.g., turning on a lamp, arming a        security panel, etc.) rather than for system configuration tasks        such as adding a new device or user.    -   PC or browser-based “widget” containers 208 that present        integrated security system service content, as well as other        third-party content, in simple, targeted ways (e.g. a widget        that resides on a PC desktop and shows live video from a single        in-home camera). “Widget” as used herein means applications or        programs in the system.    -   Touchscreen home security keypads 208 and advanced in-home        devices that present a variety of content widgets via an        intuitive touchscreen user interface.    -   Notification recipients 210 (e.g., cell phones that receive        SMS-based notifications when certain events occur (or don't        occur), email clients that receive an email message with similar        information, etc.).    -   Custom-built clients (not shown) that access the iConnect web        services XML API to interact with users' home security and        self-monitoring information in new and unique ways. Such clients        could include new types of mobile devices, or complex        applications where integrated security system content is        integrated into a broader set of application features.    -   In addition to the end-user clients, the iConnect servers 104        support PC browser-based Service Management clients that manage        the ongoing operation of the overall service. These clients run        applications that handle tasks such as provisioning, service        monitoring, customer support and reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which a gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is not solimited:

-   -   A Registry Manager 220 defines and manages users and networks.        This component is responsible for the creation, modification and        termination of users and networks. It is also where a user's        access to networks is defined.    -   A Network Manager 222 defines and manages security and        self-monitoring devices that are deployed on a network (site).        This component handles the creation, modification, deletion and        configuration of the devices, as well as the creation of        automations, schedules and notification rules associated with        those devices.    -   A Data Manager 224 manages access to current and logged state        data for an existing network and its devices. This component        specifically does not provide any access to network management        capabilities, such as adding new devices to a network, which are        handled exclusively by the Network Manager 222.    -   To achieve optimal performance for all types of queries, data        for current device states is stored separately from historical        state data (a.k.a. “logs”) in the database. A Log Data Manager        226 performs ongoing transfers of current device state data to        the historical data log tables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

-   -   An iHub Manager 228 directly manages all communications with        gateway clients, including receiving information about device        state changes, changing the configuration of devices, and        pushing new versions of the gateway client to the hardware it is        running on.    -   A Notification Manager 230 is responsible for sending all        notifications to clients via SMS (mobile phone messages), email        (via a relay server like an SMTP email server), etc.    -   An Alarm and CMS Manager 232 sends critical server-generated        alarm events to the home security Central Monitoring Station        (CMS) and manages all other communications of integrated        security system service data to and from the CMS.    -   The Element Management System (EMS) 234 is an iControl Business        Component that manages all activities associated with service        installation, scaling and monitoring, and filters and packages        service operations data for use by service management        applications. The SNMP MIBs published by the EMS can also be        incorporated into any third party monitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

-   -   A Registry Manager API 252 provides access to the Registry        Manager Business Component's functionality, allowing management        of networks and users.    -   A Network Manager API 254 provides access to the Network Manager        Business Component's functionality, allowing management of        devices on a network.    -   A Data Manager API 256 provides access to the Data Manager        Business Component's functionality, such as setting and        retrieving (current and historical) data about device states.    -   A Provisioning API 258 provides a simple way to create new        networks and configure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect 260, is aflexible, standards-based mechanism for defining the properties of newdevices and how they can be managed. Although the format is flexibleenough to allow the addition of any type of future device, pre-definedXML profiles are currently available for adding common types of devicessuch as sensors (SensorConnect), home security panels (PanelConnect) andIP cameras (CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

-   -   An iControl Activation Application 270 that delivers the first        application that a user sees when they set up the integrated        security system service. This wizard-based web browser        application securely associates a new user with a purchased        gateway and the other devices included with it as a kit (if        any). It primarily uses functionality published by the        Provisioning API.    -   An iControl Web Portal Application 272 runs on PC browsers and        delivers the web-based interface to the integrated security        system service. This application allows users to manage their        networks (e.g. add devices and create automations) as well as to        view/change device states, and manage pictures and videos.        Because of the wide scope of capabilities of this application,        it uses three different Business Component APIs that include the        Registry Manager API, Network Manager API, and Data Manager API,        but the embodiment is not so limited.    -   An iControl Mobile Portal 274 is a small-footprint web-based        interface that runs on mobile phones and PDAs. This interface is        optimized for remote viewing of device states and        pictures/videos rather than network management. As such, its        interaction with the Business Components is primarily via the        Data Manager API.    -   Custom portals and targeted client applications can be provided        that leverage the same Business Component APIs used by the above        applications.    -   A Content Manager Application Component 276 delivers content to        a variety of clients. It sends multimedia-rich user interface        components to widget container clients (both PC and        browser-based), as well as to advanced touchscreen keypad        clients. In addition to providing content directly to end-user        devices, the Content Manager 276 provides widget-based user        interface components to satisfy requests from other Application        Components such as the iControl Web 272 and Mobile 274 portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

-   -   A Service Management Application 280 allows service        administrators to perform activities associated with service        installation, scaling and monitoring/alerting. This application        interacts heavily with the Element Management System (EMS)        Business Component to execute its functionality, and also        retrieves its monitoring data from that component via protocols        such as SNMP MIBs.    -   A Kitting Application 282 is used by employees performing        service provisioning tasks. This application allows home        security and self-monitoring devices to be associated with        gateways during the warehouse kitting process.    -   A CSR Application and Report Generator 284 is used by personnel        supporting the integrated security system service, such as CSRs        resolving end-user issues and employees enquiring about overall        service usage. Pushes of new gateway firmware to deployed        gateways is also managed by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can compliment or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes a gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

FIG. 3 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the gateway and iConnect        server in order to prevent unauthorized spoofing and attacks.        Data sent from the iConnect server to the gateway application        (or vice versa) is digitally signed as an additional layer of        security. Digital signing provides both authentication and        validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The gateway provides for 128-bit        SSL encapsulation of the user picture and video data sent over        the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A gateway-enabled device is assigned a unique activation key for        activation with an iConnect server. This ensures that only valid        gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying gateway-enabled devices        have the knowledge that only a gateway with the correct serial        number and activation key can be activated for use with an        iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8 amset temperature to 65 degrees Fahrenheit, etc.). Though the schedulesare programmed and reside at the iConnect server level they are sent tothe scheduler within the gateway application. The Schedules Engine 318then interfaces with SensorConnect 312 to ensure that scheduled eventsoccur at precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 4 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gateway 102, the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Broadband 412, GPRS414 and/or Public Switched Telephone Network (PTSN) 416 to name a few.In general, broadband communication 412 is the primary means ofconnection between the gateway 102 and the iConnect server 104 and theGPRS/CDMA 414 and/or PSTN 416 interfaces acts as back-up for faulttolerance in case the user's broadband connection fails for whateverreason, but the embodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 5 is a block diagram 500 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255-257 are coupled to the gateway 102 using a securenetwork coupling or connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption). Thenetwork coupling or connection between the gateway 102 and the networkdevices 255-257 is a private coupling or connection in that it issegregated from any other network couplings or connections. The gateway102 is coupled to the premise router/firewall 252 via a coupling with apremise LAN 250. The premise router/firewall 252 is coupled to abroadband modem 251, and the broadband modem 251 is coupled to a WAN 200or other network outside the premise. The gateway 102 thus enables orforms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 250 of the hostpremises. The gateway sub-network can include, but is not limited to,any number of other devices like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The gateway 102manages or controls the sub-network separately from the LAN 250 andtransfers data and information between components of the sub-network andthe LAN 250/WAN 200, but is not so limited. Additionally, other networkdevices 254 can be coupled to the LAN 250 without being coupled to thegateway 102.

FIG. 6 is a block diagram 600 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255-257 are coupled to the gateway 102. The networkcoupling or connection between the gateway 102 and the network devices255-257 is a private coupling or connection in that it is segregatedfrom any other network couplings or connections. The gateway 102 iscoupled or connected between the premise router/firewall 252 and thebroadband modem 251. The broadband modem 251 is coupled to a WAN 200 orother network outside the premise, while the premise router/firewall 252is coupled to a premise LAN 250. As a result of its location between thebroadband modem 251 and the premise router/firewall 252, the gateway 102can be configured or function as the premise router routing specifieddata between the outside network (e.g., WAN 200) and the premiserouter/firewall 252 of the LAN 250. As described above, the gateway 102in this configuration enables or forms a separate wireless network, orsub-network, that includes the network or premise devices 255-257 and iscoupled or connected between the LAN 250 of the host premises and theWAN 200. The gateway sub-network can include, but is not limited to, anynumber of network or premise devices 255-257 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The gateway 102 manages or controls the sub-network separately fromthe LAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the gateway 102.

The examples described above with reference to FIGS. 5 and 6 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premise network.

The integrated security system of an embodiment includes a touchscreen(also referred to as the iControl touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premise. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premise may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection.

The system of an embodiment includes a touchscreen with a configurablesoftware user interface and/or a gateway device (e.g., iHub) thatcouples or connects to a premise security panel through a wired orwireless connection, and a remote server that provides access to contentand information from the premises devices to a user when they are remotefrom the home. The touchscreen supports broadband and/or WAN wirelessconnectivity. In this embodiment, the touchscreen incorporates an IPbroadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or acellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreendescribed herein can be used as one or more of a security systeminterface panel and a network user interface (UI) that provides aninterface to interact with a network (e.g., LAN, WAN, internet, etc.).

The touchscreen of an embodiment provides an integrated touchscreen andsecurity panel as an all-in-one device. Once integrated using thetouchscreen, the touchscreen and a security panel of a premise securitysystem become physically co-located in one device, and the functionalityof both may even be co-resident on the same CPU and memory (though thisis not required).

The touchscreen of an embodiment also provides an integrated IP videoand touchscreen UI. As such, the touchscreen supports one or morestandard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4,M-JPEG, etc.). The touchscreen UI then provides a mechanism (such as acamera or video widget) to play video. In an embodiment the video isstreamed live from an IP video camera. In other embodiments the videocomprises video clips or photos sent from an IP camera or from a remotelocation.

The touchscreen of an embodiment provides a configurable user interfacesystem that includes a configuration supporting use as a securitytouchscreen. In this embodiment, the touchscreen utilizes a modular userinterface that allows components to be modified easily by a serviceprovider, an installer, or even the end user. Examples of such a modularapproach include using Flash widgets, HTML-based widgets, or otherdownloadable code modules such that the user interface of thetouchscreen can be updated and modified while the application isrunning. In an embodiment the touchscreen user interface modules can bedownloaded over the internet. For example, a new security configurationwidget can be downloaded from a standard web server, and the touchscreenthen loads such configuration app into memory, and inserts it in placeof the old security configuration widget. The touchscreen of anembodiment is configured to provide a self-install user interface.

Embodiments of the networked security touchscreen system describedherein include a touchscreen device with a user interface that includesa security toolbar providing one or more functions including arm,disarm, panic, medic, and alert. The touchscreen therefore includes atleast one screen having a separate region of the screen dedicated to asecurity toolbar. The security toolbar of an embodiment is present inthe dedicated region at all times that the screen is active.

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing home-basedfunctions. The home-based functions of an embodiment include managing,viewing, and/or controlling IP video cameras. In this embodiment,regions of the home screen are allocated in the form of widget icons;these widget icons (e.g. for cameras, thermostats, lighting, etc)provide functionality for managing home systems. So, for example, adisplayed camera icon, when selected, launches a Camera Widget, and theCamera widget in turn provides access to video from one or more cameras,as well as providing the user with relevant camera controls (take apicture, focus the camera, etc.)

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing, viewing, and/orcontrolling internet-based content or applications. For example, theWidget Manager UI presents a region of the home screen (up to andincluding the entire home screen) where internet widgets icons such asweather, sports, etc. may be accessed). Each of these icons may beselected to launch their respective content services.

The touchscreen of an embodiment is integrated into a premise networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with another network (e.g., WAN, LANof the host premises, etc.). The sub-network enabled by the gatewayoptimizes the installation process for IP devices, like the touchscreen,that couple or connect to the sub-network by segregating these IPdevices from other such devices on the network. This segregation of theIP devices of the sub-network further enables separate security andprivacy policies to be implemented for these IP devices so that, wherethe IP devices are dedicated to specific functions (e.g., security), thesecurity and privacy policies can be tailored specifically for thespecific functions. Furthermore, the gateway and the sub-network itforms enables the segregation of data traffic, resulting in faster andmore efficient data flow between components of the host network,components of the sub-network, and between components of the sub-networkand components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisesecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g SetAlarmLevel (int level, int partition, char*accessCode)). Power control drivers are also provided.

FIG. 7A is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g., Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premise security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premise security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with the premisesecurity system, these applications make use of the same fundamentalapplication facilities as any other ‘widget’, application facilitiesthat include graphical layout, interactivity, application handoff,screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager.

Referring to FIG. 7A, the touchscreen system of an embodiment is builton a tiered architecture, with defined interfaces between theApplication/Presentation Layer 702 (the Application Engine) on the top,the Core Engine 706 in the middle, and the security panel API 724 andgateway API 728 at the lower level. The architecture is configured toprovide maximum flexibility and ease of maintenance.

The touchscreen of an embodiment is a modular touchscreen platform thatenables dynamic reconfiguration of the touchscreen for differentfunctions or functionality. The touchscreen platform of an embodimentincludes the touchscreen display and one or more modules that eachenable different functions in the touchscreen platform. Each module isremoveably coupled (e.g., plug-in, etc.) to the touchscreen, but is notso limited. The modules therefore provide different functionalitythrough the touchscreen depending on current needs of the user. Thetouchscreen platform can be used as an in-home consumer touchscreen withuses including, for example, home management, including energymanagement, security, surveillance, health monitoring, elder care andother consumer applications, to name a few.

The touchscreen platform of an embodiment enables the provision of newfeatures and capabilities via the touchscreen through the use ofdifferent modules that interface and function with a common touchscreenor display platform. The modules can be connected to or disconnectedfrom the touchscreen by a user and do not require any reconfiguration ofthe touchscreen by the user. In this manner, new modules supporting newfunctionality can be produced and used by the user with the touchscreenwithout any need to replace the touchscreen. The modules can bestand-alone modules or, alternatively, the modules can communicate witha remote device and/or system to provide desired functionality.

The touchscreen platform includes a display device having a receptacleor region that accepts or receives a module. The module includes thecircuitry, hardware, and/or firmware to support a function thatcorresponds to the module. Modules can support any desired functionalitywithout impacting the size, weight or cost of the base display unit. Forexample a security module enables the touchscreen platform with securitypanel functionality such that the touchscreen functions as a securitysystem, or interfaces with a security system. The modules can alsoenable the touchscreen platform with functionality or featurescorresponding to a thermostat, energy management device, rechargeablebattery support, elder-care monitoring, and/or remote health monitoringdevice, to name just a few.

FIG. 7B is a block diagram of a touchscreen 700B and module 760, underan alternative embodiment. The touchscreen 700B generally includes anapplication/presentation layer 702 with a resident application 704, anda core engine 706. The touchscreen 700 also includes one or more of thefollowing, but is not so limited: applications of premium services 710,widgets 712, a caching proxy 714, network security 716, networkinterface 718, security object 720, applications supporting devices 722,PanelConnect API 724, a gateway interface 726, module interface 750,module 760, and one or more ports 728.

The touchscreen 700B of this embodiment includes the PanelConnect API724 coupled to a port 728 by which the touchscreen componentscommunicate with a security system controller as described herein. Thetouchscreen 700B of this embodiment also includes the gateway interface726 coupled to a port 728 by which the touchscreen componentscommunicate with an integrated security system as described herein. Thetouchscreen 700B also includes the module interface 750 coupled to themodule 760.

The platform including the module 760 coupled or connected to thetouchscreen 700B of an embodiment includes the circuitry, hardware,and/or firmware to function as a stand-alone device providingfunctionality that corresponds to the module. Modules can support anydesired functionality. Thus, the platform including the touchscreen 700Band module 760 function in a stand-alone manner as security system,thermostat, energy management device, rechargeable battery support,elder-care monitoring, and/or remote health monitoring device, to namejust a few. More specifically, in the context of a security system asdescribed herein, when the touchscreen 700B and module 760 function as asecurity system, the touchscreen 700B and module 760 collectivelyinclude the functionality of the security system components describedelsewhere herein.

FIG. 7C is a block diagram of a touchscreen 700C and module 760, underanother alternative embodiment. The touchscreen 700C generally includesan application/presentation layer 702 with a resident application 704,and a core engine 706. The touchscreen 700C also includes one or more ofthe following, but is not so limited: applications of premium services710, widgets 712, a caching proxy 714, network security 716, networkinterface 718, security object 720, applications supporting devices 722,PanelConnect API 724, a gateway interface 726, module interface 750, andthe module 760.

The touchscreen 700C of this embodiment includes the PanelConnect API724 coupled to the module 760 by which the touchscreen componentscommunicate with a security system controller as described herein. Thetouchscreen 700C of this embodiment also includes the gateway interface726 coupled to the module 760 by which the touchscreen componentscommunicate with an integrated security system as described herein. Thetouchscreen 700C also includes the module interface 750 coupled to themodule 760.

The platform including the module 760 coupled or connected to thetouchscreen 700C of an embodiment includes the circuitry, hardware,and/or firmware to function as a stand-alone device providingfunctionality that corresponds to the module. Modules can support anydesired functionality. Thus, the platform including the touchscreen 700Cand module 760 function in a stand-alone manner as security system,thermostat, energy management device, rechargeable battery support,elder-care monitoring, and/or remote health monitoring device, to namejust a few. More specifically, in the context of a security system asdescribed herein, when the touchscreen 700C and module 760 function as asecurity system, the touchscreen 700C and module 760 collectivelyinclude the functionality of the security system components describedelsewhere herein.

FIG. 7D is a block diagram of a touchscreen 700D and module 760, underanother alternative embodiment. The touchscreen 700D generally includesan application/presentation layer 702 with a resident application 704,and a core engine 706. The touchscreen 700D also includes one or more ofthe following, but is not so limited: applications of premium services710, widgets 712, a caching proxy 714, network security 716, networkinterface 718, security object 720, applications supporting devices 722,PanelConnect API 724, a module interface 750, and the module 760.

The touchscreen 700D of this embodiment includes the PanelConnect API724 coupled to a port 728 by which the touchscreen componentscommunicate with a security system controller as described herein. Thetouchscreen 700D of this embodiment also includes the module interface750 coupled to the module 760 by which the touchscreen componentscommunicate with an integrated security system as described herein.

The platform including the module 760 coupled or connected to thetouchscreen 700D of an embodiment includes the circuitry, hardware,and/or firmware to function as a stand-alone device providingfunctionality that corresponds to the module. Modules can support anydesired functionality. Thus, the platform including the touchscreen 700Dand module 760 function in a stand-alone manner as security system,thermostat, energy management device, rechargeable battery support,elder-care monitoring, and/or remote health monitoring device, to namejust a few. More specifically, in the context of a security system asdescribed herein, when the touchscreen 700D and module 760 function as asecurity system, the touchscreen 700D and module 760 collectivelyinclude the functionality of the security system components describedelsewhere herein.

FIG. 7E is a block diagram of a touchscreen 700E and module 760, underyet another alternative embodiment. The touchscreen 700E generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700E alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, module interface 750, and module760.

The platform including the touchscreen 700E and module 760 of anembodiment includes the circuitry, hardware, and/or firmware to functionas a stand-alone device providing functionality that corresponds to themodule. Modules can support any desired functionality. Thus, theplatform including the touchscreen 700E and module 760 function in astand-alone manner as security system, thermostat, energy managementdevice, rechargeable battery support, elder-care monitoring, and/orremote health monitoring device, to name just a few. More specifically,in the context of a security system as described herein, when thetouchscreen 700E and module 760 function as a security system, thetouchscreen 700E and module 760 collectively include the functionalityof the security system components and gateway described elsewhereherein.

FIG. 7F is a block diagram of a touchscreen 700F and module 760, understill another alternative embodiment. The touchscreen 700F generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700F alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, module interface 750, and module760.

The platform including the touchscreen 700F and module 760 of anembodiment includes the circuitry, hardware, and/or firmware tocommunicate with a remote device and/or system 764. In this embodimentthe touchscreen 700F, module 760 and remote device and/or system 764function cooperatively to provide functionality that corresponds to themodule. Therefore, the platform including the touchscreen 700F andmodule 760 communicate with a remote device and/or system 764 via acommunication channel 762 to cooperatively provide functionality of asecurity system, thermostat, energy management device, rechargeablebattery support, elder-care monitoring, and/or remote health monitoringdevice, to name just a few. More specifically, in the context of asecurity system as described herein, when the touchscreen 700F, module760 and remote device and/or system 764 function as a security system,the touchscreen 700F, module 760 and remote device and/or system 764collectively include the functionality of the security system componentsdescribed elsewhere herein.

FIG. 7G shows front, rear, and side views of a 4.3-inch touchscreen withmodule and a 7-inch LCD touchscreen with module, under an embodiment.The module receptacle or slot of an embodiment is located in the rear ofthe touchscreen and supports a common module form factor through astandard connector (e.g. USB, etc.), but the module receptacle is notlimited to a location on the rear of the touchscreen.

FIG. 7H shows an external module plugging into a receptacle of the7-inch touchscreen display, under an embodiment. FIG. 7I shows anexternal module plugging into a receptacle of the 4.3-inch touchscreendisplay, under an embodiment. The module form factor is common to bothdisplay sizes and thus the same modules can be used with either screensize, but the embodiment is not so limited. Once configured with amodule the touchscreen can be positioned as desired by a user. Forexample, FIG. 7J shows the touchscreen platform positioned on a tabletop, under an embodiment. FIG. 7K shows the touchscreen platform mountedon a wall, under an embodiment.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. FIG. 8 is an example screenshot 800 of anetworked security touchscreen, under an embodiment. This examplescreenshot 800 includes three interfaces or user interface (UI)components 802-806, but is not so limited. A first UI 802 of thetouchscreen includes icons by which a user controls or accessesfunctions and/or components of the security system (e.g., “Main”,“Panic”, “Medic”, “Fire”, state of the premise alarm system (e.g.,disarmed, armed, etc.), etc.); the first UI 802, which is also referredto herein as a security interface, is always presented on thetouchscreen. A second UI 804 of the touchscreen includes icons by whicha user selects or interacts with services and other network content(e.g., clock, calendar, weather, stocks, news, sports, photos, maps,music, etc.) that is accessible via the touchscreen. The second UI 804is also referred to herein as a network interface or content interface.A third UI 806 of the touchscreen includes icons by which a user selectsor interacts with additional services or components (e.g., intercomcontrol, security, cameras coupled to the system in particular regions(e.g., front door, baby, etc.) available via the touchscreen.

A component of the application engine is the Presentation Engine, whichincludes a set of libraries that implement the standards-based widgetcontent (e.g., XML, HTML, JavaScript, Flash) layout and interactivity.This engine provides the widget with interfaces to dynamically load bothgraphics and application logic from third parties, support high leveldata description language as well as standard graphic formats. The setof web content-based functionality available to a widget developer isextended by specific touchscreen functions implemented as local webservices by the Core Engine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets in the system, and enforces thebusiness and security rules required by the service provider. Forexample, the resident application determines the priority of widgets,thereby enabling a home security widget to override resource requestsfrom a less critical widget (e.g. a weather widget). The residentapplication also monitors widget behavior, and responds to client orserver requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests; although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The touchscreen of an embodiment operates wirelessly with a premisesecurity system. The touchscreen of an embodiment incorporates an RFtransceiver component that either communicates directly with the sensorsand/or security panel over the panel's proprietary RF frequency, or thetouchscreen communicates wirelessly to the gateway over 802.11,Ethernet, or other IP-based communications channel, as described indetail herein. In the latter case the gateway implements thePanelConnect interface and communicates directly to the security paneland/or sensors over wireless or wired networks as described in detailabove.

The touchscreen of an embodiment is configured to operate with multiplesecurity systems through the use of an abstracted security systeminterface. In this embodiment, the PanelConnect API can be configured tosupport a plurality of proprietary security system interfaces, eithersimultaneously or individually as described herein. In one embodiment ofthis approach, the touchscreen incorporates multiple physical interfacesto security panels (e.g. GE Security RS-485, Honeywell RF, etc.) inaddition to the PanelConnect API implemented to support multiplesecurity interfaces. The change needed to support this in PanelConnectis a configuration parameter specifying the panel type connection thatis being utilized.

So for example, the setARMState( ) function is called with an additionalparameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)).The ‘panelType’ parameter is used by the setARMState function (and inpractice by all of the PanelConnect functions) to select an algorithmappropriate to the specific panel out of a plurality of alogorithms.

The touchscreen of an embodiment is self-installable. Consequently, thetouchscreen provides a ‘wizard’ approach similar to that used intraditional computer installations (e.g. InstallShield). The wizard canbe resident on the touchscreen, accessible through a web interface, orboth. In one embodiment of a touchscreen self-installation process, theservice provider can associate devices (sensors, touchscreens, securitypanels, lighting controls, etc.) remotely using a web-basedadministrator interface.

The touchscreen of an embodiment includes a battery backup system for asecurity touchscreen. The touchscreen incorporates a standard Li-ion orother battery and charging circuitry to allow continued operation in theevent of a power outage. In an embodiment the battery is physicallylocated and connected within the touchscreen enclosure. In anotherembodiment the battery is located as a part of the power transformer, orin between the power transformer and the touchscreen.

The example configurations of the integrated security system describedabove with reference to FIGS. 5 and 6 include a gateway that is aseparate device, and the touchscreen couples to the gateway. However, inan alternative embodiment, the gateway device and its functionality canbe incorporated into the touchscreen so that the device managementmodule, which is now a component of or included in the touchscreen, isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system with the integrated touchscreen/gateway usesthe same “sandbox” network to discover and manage all IP devices coupledor connected as components of the system.

The touchscreen of this alternative embodiment integrates the componentsof the gateway with the components of the touchscreen as describedherein. More specifically, the touchscreen of this alternativeembodiment includes software or applications described above withreference to FIG. 3 . In this alternative embodiment, the touchscreenincludes the gateway application layer 302 as the main program thatorchestrates the operations performed by the gateway. A Security Engine304 of the touchscreen provides robust protection against intentionaland unintentional intrusion into the integrated security system networkfrom the outside world (both from inside the premises as well as fromthe WAN). The Security Engine 304 of an embodiment comprises one or moresub-modules or components that perform functions including, but notlimited to, the following:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the touchscreen and        iConnect server in order to prevent unauthorized spoofing and        attacks. Data sent from the iConnect server to the gateway        application (or vice versa) is digitally signed as an additional        layer of security. Digital signing provides both authentication        and validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The touchscreen provides for        128-bit SSL encapsulation of the user picture and video data        sent over the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A touchscreen-enabled device is assigned a unique activation key        for activation with an iConnect server. This ensures that only        valid gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying touchscreen-enabled        devices have the knowledge that only a gateway with the correct        serial number and activation key can be activated for use with        an iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 of the touchscreen allows forseamless and secure updates to the gateway firmware through the iControlMaintenance Application on the server 104, providing a transparent,hassle-free mechanism for the service provider to deploy new featuresand bug fixes to the installed user base. The firmware downloadmechanism is tolerant of connection loss, power interruption and userinterventions (both intentional and unintentional). Such robustnessreduces down time and customer support issues. Touchscreen firmware canbe remotely download either for one touchscreen at a time, a group oftouchscreen, or in batches.

The Automations engine 308 of the touchscreen manages the user-definedrules of interaction between the different devices (e.g. when door opensturn on the light). Though the automation rules are programmed andreside at the portal/server level, they are cached at the gateway levelin order to provide short latency between device triggers and actions.

DeviceConnect 310 of the touchscreen includes definitions of allsupported devices (e.g., cameras, security panels, sensors, etc.) usinga standardized plug-in architecture. The DeviceConnect module 310 offersan interface that can be used to quickly add support for any new deviceas well as enabling interoperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 of the touchscreen is responsible for executingthe user defined schedules (e.g., take a picture every five minutes;every day at 8 am set temperature to 65 degrees Fahrenheit, etc.).Though the schedules are programmed and reside at the iConnect serverlevel they are sent to the scheduler within the gateway application ofthe touchscreen. The Schedules Engine 318 then interfaces withSensorConnect 312 to ensure that scheduled events occur at precisely thedesired time.

The Device Management module 320 of the touchscreen is in charge of alldiscovery, installation and configuration of both wired and wireless IPdevices (e.g., cameras, etc.) coupled or connected to the system.Networked IP devices, such as those used in the integrated securitysystem, require user configuration of many IP and security parameters,and the device management module of an embodiment handles the details ofthis configuration. The device management module also manages the videorouting module described below.

The video routing engine 322 of the touchscreen is responsible fordelivering seamless video streams to the user with zero-configuration.Through a multi-step, staged approach the video routing engine uses acombination of UPnP port-forwarding, relay server routing and STUN/TURNpeer-to-peer routing.

FIG. 9 is a block diagram 900 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255, 256, 957 are coupled to the touchscreen 902 using asecure network connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption), andthe touchscreen 902 coupled to the premise router/firewall 252 via acoupling with a premise LAN 250. The premise router/firewall 252 iscoupled to a broadband modem 251, and the broadband modem 251 is coupledto a WAN 200 or other network outside the premise. The touchscreen 902thus enables or forms a separate wireless network, or sub-network, thatincludes some number of devices and is coupled or connected to the LAN250 of the host premises. The touchscreen sub-network can include, butis not limited to, any number of other devices like WiFi IP cameras,security panels (e.g., IP-enabled), and IP devices, to name a few. Thetouchscreen 902 manages or controls the sub-network separately from theLAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 902.

FIG. 10 is a block diagram 1000 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255, 256, 1057 are coupled to the touchscreen 1002,and the touchscreen 1002 is coupled or connected between the premiserouter/firewall 252 and the broadband modem 251. The broadband modem 251is coupled to a WAN 200 or other network outside the premise, while thepremise router/firewall 252 is coupled to a premise LAN 250. As a resultof its location between the broadband modem 251 and the premiserouter/firewall 252, the touchscreen 1002 can be configured or functionas the premise router routing specified data between the outside network(e.g., WAN 200) and the premise router/firewall 252 of the LAN 250. Asdescribed above, the touchscreen 1002 in this configuration enables orforms a separate wireless network, or sub-network, that includes thenetwork or premise devices 255, 156, 1057 and is coupled or connectedbetween the LAN 250 of the host premises and the WAN 200. Thetouchscreen sub-network can include, but is not limited to, any numberof network or premise devices 255, 256, 1057 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The touchscreen 1002 manages or controls the sub-network separatelyfrom the LAN 250 and transfers data and information between componentsof the sub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 1002.

The gateway of an embodiment, whether a stand-along component orintegrated with a touchscreen, enables couplings or connections and thusthe flow or integration of information between various components of thehost premises and various types and/or combinations of IP devices, wherethe components of the host premises include a network (e.g., LAN) and/ora security system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

In an example embodiment, FIG. 11 is a flow diagram 1100 for integrationor installation of an IP device into a private network environment,under an embodiment. The IP device includes any IP-capable device which,for example, includes the touchscreen of an embodiment. The variables ofan embodiment set at time of installation include, but are not limitedto, one or more of a private SSID/Password, a gateway identifier, asecurity panel identifier, a user account TS, and a Central MonitoringStation account identification.

An embodiment of the IP device discovery and management begins with auser or installer activating 1102 the gateway and initiating 1104 theinstall mode of the system. This places the gateway in an install mode.Once in install mode, the gateway shifts to a default (Install) Wificonfiguration. This setting will match the default setting for otherintegrated security system-enabled devices that have been pre-configuredto work with the integrated security system. The gateway will then beginto provide 1106 DHCP addresses for these IP devices. Once the deviceshave acquired a new DHCP address from the gateway, those devices areavailable for configuration into a new secured Wifi network setting.

The user or installer of the system selects 1108 all devices that havebeen identified as available for inclusion into the integrated securitysystem. The user may select these devices by their unique IDs via a webpage, Touchscreen, or other client interface. The gateway provides 1110data as appropriate to the devices. Once selected, the devices areconfigured 1112 with appropriate secured Wifi settings, including SSIDand WPA/WPA-2 keys that are used once the gateway switches back to thesecured sandbox configuration from the “Install” settings. Othersettings are also configured as appropriate for that type of device.Once all devices have been configured, the user is notified and the usercan exit install mode. At this point all devices will have beenregistered 1114 with the integrated security system servers.

The installer switches 1116 the gateway to an operational mode, and thegateway instructs or directs 1118 all newly configured devices to switchto the “secured” Wifi sandbox settings. The gateway then switches 1120to the “secured” Wifi settings. Once the devices identify that thegateway is active on the “secured” network, they request new DHCPaddresses from the gateway which, in response, provides 1122 the newaddresses. The devices with the new addresses are then operational 1124on the secured network.

In order to ensure the highest level of security on the secured network,the gateway can create or generate a dynamic network securityconfiguration based on the unique ID and private key in the gateway,coupled with a randomizing factor that can be based on online time orother inputs. This guarantees the uniqueness of the gateway securednetwork configuration.

To enable the highest level of performance, the gateway analyzes the RFspectrum of the 802.11x network and determines which frequencyband/channel it should select to run.

An alternative embodiment of the camera/IP device management processleverages the local ethernet connection of the sandbox network on thegateway. This alternative process is similar to the Wifi discoveryembodiment described above, except the user connects the targeted deviceto the ethernet port of the sandbox network to begin the process. Thisalternative embodiment accommodates devices that have not beenpre-configured with the default “Install” configuration for theintegrated security system.

This alternative embodiment of the IP device discovery and managementbegins with the user/installer placing the system into install mode. Theuser is instructed to attach an IP device to be installed to the sandboxEthernet port of the gateway. The IP device requests a DHCP address fromthe gateway which, in response to the request, provides the address. Theuser is presented the device and is asked if he/she wants to install thedevice. If yes, the system configures the device with the secured Wifisettings and other device-specific settings (e.g., camera settings forvideo length, image quality etc.). The user is next instructed todisconnect the device from the ethernet port. The device is nowavailable for use on the secured sandbox network.

FIG. 12 is a block diagram showing communications among integrated IPdevices of the private network environment, under an embodiment. The IPdevices of this example include a security touchscreen 1203, gateway1202 (e.g., “iHub”), and security panel (e.g., “Security Panel 1”,“Security Panel 2”, “Security Panel n”), but the embodiment is not solimited. In alternative embodiments any number and/or combination ofthese three primary component types may be combined with othercomponents including IP devices and/or security system components. Forexample, a single device which comprises an integrated gateway,touchscreen, and security panel is merely another embodiment of theintegrated security system described herein. The description thatfollows includes an example configuration that includes a touchscreenhosting particular applications. However, the embodiment is not limitedto the touchscreen hosting these applications, and the touchscreenshould be thought of as representing any IP device.

Referring to FIG. 12 , the touchscreen 1203 incorporates an application1210 that is implemented as computer code resident on the touchscreenoperating system, or as a web-based application running in a browser, oras another type of scripted application (e.g., Flash, Java, VisualBasic, etc.). The touchscreen core application 1210 represents thisapplication, providing user interface and logic for the end user tomanage their security system or to gain access to networked informationor content (Widgets). The touchscreen core application 1210 in turnaccesses a library or libraries of functions to control the localhardware (e.g. screen display, sound, LEDs, memory, etc.) as well asspecialized librarie(s) to couple or connect to the security system.

In an embodiment of this security system connection, the touchscreen1203 communicates to the gateway 1202, and has no direct communicationwith the security panel. In this embodiment, the touchscreen coreapplication 1210 accesses the remote service APIs 1212 which providesecurity system functionality (e.g. ARM/DISARM panel, sensor state,get/set panel configuration parameters, initiate or get alarm events,etc.). In an embodiment, the remote service APIs 1212 implement one ormore of the following functions, but the embodiment is not so limited:Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”);sensorState=getSensors(type=“ALL|SensorName|SensorNameList”);result=setSensorState(SensorName, parameters=“Option1, Options2, . . .Option n”); interruptHandler=SensorEvent( ); and,interruptHandler=alarmEvent( ).

Functions of the remote service APIs 1212 of an embodiment use a remotePanelConnect API 1224 which resides in memory on the gateway 1202. Thetouchscreen 1203 communicates with the gateway 1202 through a suitablenetwork interface such as an Ethernet or 802.11 RF connection, forexample. The remote PanelConnect API 1224 provides the underlyingSecurity System Interfaces 1226 used to communicate with and control oneor more types of security panel via wired link 1230 and/or RF link 3.The PanelConnect API 1224 provides responses and input to the remoteservices APIs 1226, and in turn translates function calls and data toand from the specific protocols and functions supported by a specificimplementation of a Security Panel (e.g. a GE Security Simon XT orHoneywell Vista 20P). In an embodiment, the PanelConnect API 1224 uses a345 MHz RF transceiver or receiver hardware/firmware module tocommunicate wirelessly to the security panel and directly to a set of345 MHz RF-enabled sensors and devices, but the embodiment is not solimited.

The gateway of an alternative embodiment communicates over a wiredphysical coupling or connection to the security panel using the panel'sspecific wired hardware (bus) interface and the panel's bus-levelprotocol.

In an alternative embodiment, the Touchscreen 1203 implements the samePanelConnect API 1214 locally on the Touchscreen 1203, communicatingdirectly with the Security Panel 2 and/or Sensors 2 over the proprietaryRF link or over a wired link for that system. In this embodiment theTouchscreen 1203, instead of the gateway 1202, incorporates the 345 MHzRF transceiver to communicate directly with Security Panel 2 or Sensors2 over the RF link 2. In the case of a wired link the Touchscreen 1203incorporates the real-time hardware (e.g. a PIC chip and RS232-variantserial link) to physically connect to and satisfy the specific bus-leveltiming requirements of the SecurityPanel2.

In yet another alternative embodiment, either the gateway 1202 or theTouchscreen 1203 implements the remote service APIs. This embodimentincludes a Cricket device (“Cricket”) which comprises but is not limitedto the following components: a processor (suitable for handling 802.11protocols and processing, as well as the bus timing requirements ofSecurityPanel1); an 802.11 (WiFi) client IP interface chip; and, aserial bus interface chip that implements variants of RS232 or RS485,depending on the specific Security Panel.

The Cricket also implements the full PanelConnect APIs such that it canperform the same functions as the case where the gateway implements thePanelConnect APIs. In this embodiment, the touchscreen core application1210 calls functions in the remote service APIs 1212 (such assetArmState( )). These functions in turn couple or connect to the remoteCricket through a standard IP connection (“Cricket IP Link”) (e.g.,Ethernet, Homeplug, the gateway's proprietary Wifi network, etc.). TheCricket in turn implements the PanelConnect API, which responds to therequest from the touchscreen core application, and performs theappropriate function using the proprietary panel interface. Thisinterface uses either the wireless or wired proprietary protocol for thespecific security panel and/or sensors.

An example use case that illustrates the use of the touchscreenembodiments described above is a panic alarm. FIG. 13 is a data flowdiagram for a panic alarm 1300, under an embodiment. In order toactivate a panic alarm on the touchscreen, the user presses one of thepanic alarm buttons, and confirms the alarm with a second button press(Step 1). When the alarm is activated, in Step 2 the touchscreen sendsthe alarm signal to both the security panel and the gateway (using thePanelConnect or remote Svc API interface described above).

In Step 3, the security panel alerts other keypads and touchscreens(once again through the PanelConnect interface) of the alarm condition,and flashes lights/sounds sirens as appropriate. The gateway or securitypanel calls the CMS on the hard-wired phone line. Simultaneously, thegateway sends a signal to the iConnect Server system over the broadbandconnection and, if so configured, uses GPRS to call a cell phone relaystation with the alarm data. In Step 4, the iConnect Server systemroutes the information, formatted using an industry standard alarmformat such as ContactID or SIA, to a suitable broadband receiver in theCMS (for example the DSC Surguard broadband alarm receiver, or directlyto the CMS automation software server). At the same time, in Step 5 theserver system will also call a phone, send an SMS message, or send anemail to any designated receiver.

The second example use case involving the touchscreen is a deviceinstallation example. FIG. 14 is a data flow diagram for deviceinstallation 1400, under an embodiment. To make installation easier, theuser can receive feedback from the touchscreen about what devices havebeen programmed in to the system, and the system automatically couplesor connects to the CMS to configure the sensors on the back end.

As a data flow, in Step 1 the installer initiates entry into sensorlearning mode by activating the installation UI on the touchscreen. Whenthe installer triggers or otherwise activates a sensor in Step 2, thegateway picks up the wireless communication from the sensor and pushesinformation about the sensor to the touchscreen (Step 3). At this point,the installer can program the specific name of the sensor and its zones.This process is repeated for all of the sensors in the system. Once allsensors have been ‘learned’ in this way, the information is transmittedvia internet or cellular IP networks to the iConnect server. The sensorinformation is associated with a ‘network’ (e.g., a location), but hasnot yet been associated with a specific user or account. After thisstep, the installer then creates a user account, and the previouslycreated network is then associated with that account in the iConnectuser database. This embodiment allows systems, devices, touchscreens,panels, and the like to be pre-associated, packaged, and/or installedwithout reference to a user or subscriber account.

To ensure that the security system is operating properly, it is next putinto test mode. As the installer opens and closes the sensor, thetouchscreen places a ‘check’ next to the name of the sensor. At the sametime, in Step 4 the gateway pushes the open/close information to theiConnect servers, which alert the CMS to verify that a signal has beenreceived for the sensor on the back end. In Step 5, the CMS acknowledgesthat the sensor has been installed correctly and is operational, andthat acknowledgement is pushed back through the system. When the systeminstallation is finished, the iConnect servers send a notification ofthe installation, along with sensor set up information, and electronicverification of the test process for all sensors to the serviceprovider.

Yet another example use case involving the touchscreen is a cameraevent. FIG. 15 is a data flow diagram for a camera event 1500, under anembodiment. Cameras can be integrated with alerts that are generated bysensor events. For example, a consumer who wishes to see who is at herfront door would set up the front door sensor to trigger an iControlNotification to the touchscreen, signifying a camera alert. When thesensor is activated, a pop-up appears on the touchscreen telling theuser that the front door sensor has been activated, and asking the userif he or she would like to view the video.

The flow diagram for the camera event 1500 shows the flow of data fromthe sensor to the security panel and the gateway during a camera event.The gateway receives information regarding automation ‘rules’ betweencamera and sensor event from the iConnect servers as a part of theperiodic state updates that occur between gateway client and server.

In Step 1 a sensor or multiple sensors are triggered. In Step 2 thegateway and/or Security Panel receives notification that a sensor statehas changed through a network connection (wired or wireless) with thesensor, and if a rule exists for that device or set of devices, thetouchscreen is then alerted via the PanelConnect interface runningeither locally on the touchscreen or remotely on the gateway. In Step 3,the touchscreen puts up the alert and, if requested, opens a videostream from the camera. In the event that the touchscreen is in aquiescent mode instead of a dialog popup the IP video is immediatelydisplayed, and an audible alert may sound as an option in thenotification.

Step 3 of the data flow also shows an alternate route over which thegateway, if so configured, can send the sensor information the iControlservers (Step 4), which in turn forward the information in the form ofan SMS alert or direct IP notification to a cell phone (Step 5). Thecell phone user could then set up a video stream from the camera.

FIG. 16 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment. Operations begin when the system is powered on1610, involving at a minimum the power-on of the gateway device, andoptionally the power-on of the connection between the gateway device andthe remote servers. The gateway device initiates 1620 a software and RFsequence to locate the extant security system. The gateway and installerinitiate and complete 1630 a sequence to ‘learn’ the gateway into thesecurity system as a valid and authorized control device. The gatewayinitiates 1640 another software and RF sequence of instructions todiscover and learn the existence and capabilities of existing RF deviceswithin the extant security system, and store this information in thesystem. These operations under the system of an embodiment are describedin further detail below.

Unlike conventional systems that extend an existing security system, thesystem of an embodiment operates utilizing the proprietary wirelessprotocols of the security system manufacturer. In one illustrativeembodiment, the gateway is an embedded computer with an IP LAN and WANconnection and a plurality of RF transceivers and software protocolmodules capable of communicating with a plurality of security systemseach with a potentially different RF and software protocol interface.After the gateway has completed the discovery and learning 1640 ofsensors and has been integrated 1650 as a virtual control device in theextant security system, the system becomes operational. Thus, thesecurity system and associated sensors are presented 1650 as accessibledevices to a potential plurality of user interface subsystems.

The system of an embodiment integrates 1660 the functionality of theextant security system with other non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms, which may be controlled via RF, wired, or powerline-basednetworking mechanisms supported by the gateway or servers.

The system of an embodiment provides a user interface subsystem 1670enabling a user to monitor, manage, and control the system andassociated sensors and security systems. In an embodiment of the system,a user interface subsystem is an HTML/WL/Javascript/Java/AJAX/Flashpresentation of a monitoring and control application, enabling users toview the state of all sensors and controllers in the extant securitysystem from a web browser or equivalent operating on a computer, PDA,mobile phone, or other consumer device.

In another illustrative embodiment of the system described herein, auser interface subsystem is an HTML/XML/Javascript/Java/AJAXpresentation of a monitoring and control application, enabling users tocombine the monitoring and control of the extant security system andsensors with the monitoring and control of non-security devicesincluding but not limited to IP cameras, touchscreens, lightingcontrols, door locking mechanisms.

In another illustrative embodiment of the system described herein, auser interface subsystem is a mobile phone application enabling users tomonitor and control the extant security system as well as othernon-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application running on a keypad ortouchscreen device enabling users to monitor and control the extantsecurity system as well as other non-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application operating on a TV or set-topbox connected to a TV enabling users to monitor and control the extantsecurity system as well as other non-security devices.

FIG. 17 is a block diagram of an integrated security system 1700wirelessly interfacing to proprietary security systems, under anembodiment. A security system 1710 is coupled or connected to a Gateway1720, and from Gateway 1720 coupled or connected to a plurality ofinformation and content sources across a network 1730 including one ormore web servers 1740, system databases 1750, and applications servers1760. While in one embodiment network 1730 is the Internet, includingthe World Wide Web, those of skill in the art will appreciate thatnetwork 1730 may be any type of network, such as an intranet, anextranet, a virtual private network (VPN), a mobile network, or anon-TCP/IP based network.

Moreover, other elements of the system of an embodiment may beconventional, well-known elements that need not be explained in detailherein. For example, security system 1710 could be any type home orbusiness security system, such devices including but not limited to astandalone RF home security system or a non-RF-capable wired homesecurity system with an add-on RF interface module. In the integratedsecurity system 1700 of this example, security system 1710 includes anRF-capable wireless security panel (WSP) 1711 that acts as the mastercontroller for security system 1710. Well-known examples of such a WSPinclude the GE Security Concord, Networx, and Simon panels, theHoneywell Vista and Lynx panels, and similar panels from DSC and Napco,to name a few. A wireless module 1714 includes the RF hardware andprotocol software necessary to enable communication with and control ofa plurality of wireless devices 1713. WSP 1711 may also manage wireddevices 1714 physically connected to WSP 1711 with an RS232 or RS485 orEthernet connection or similar such wired interface.

In an implementation consistent with the systems and methods describedherein, Gateway 1720 provides the interface between security system 1710and LAN and/or WAN for purposes of remote control, monitoring, andmanagement. Gateway 1720 communicates with an external web server 1740,database 1750, and application server 1760 over network 1730 (which maycomprise WAN, LAN, or a combination thereof). In this example system,application logic, remote user interface functionality, as well as userstate and account are managed by the combination of these remoteservers. Gateway 1720 includes server connection manager 1721, asoftware interface module responsible for all server communication overnetwork 1730. Event manager 1722 implements the main event loop forGateway 1720, processing events received from device manager 1724(communicating with non-security system devices including but notlimited to IP cameras, wireless thermostats, or remote door locks).Event manager 1722 further processes events and control messages fromand to security system 1710 by utilizing WSP manager 1723.

WSP manager 1723 and device manager 1724 both rely upon wirelessprotocol manager 1726 which receives and stores the proprietary orstandards-based protocols required to support security system 1710 aswell as any other devices interfacing with gateway 1720. WSP manager1723 further utilizes the comprehensive protocols and interfacealgorithms for a plurality of security systems 1710 stored in the WSP DBclient database associated with wireless protocol manager 1726. Thesevarious components implement the software logic and protocols necessaryto communicate with and manager devices and security systems 1710.Wireless Transceiver hardware modules 1725 are then used to implementthe physical RF communications link to such devices and security systems1710. An illustrative wireless transceiver 1725 is the GE SecurityDialog circuit board, implementing a 319.5 MHz two-way RF transceivermodule. In this example, RF Link 1770 represents the 319.5 MHz RFcommunication link, enabling gateway 1720 to monitor and control WSP1711 and associated wireless and wired devices 1713 and 1714,respectively.

In one embodiment, server connection manager 1721 requests and receivesa set of wireless protocols for a specific security system 1710 (anillustrative example being that of the GE Security Concord panel andsensors) and stores them in the WSP DB portion of the wireless protocolmanager 1726. WSP manager 1723 then utilizes such protocols fromwireless protocol manager 1726 to initiate the sequence of processesdetailed in FIG. 16 and FIG. 17 for learning gateway 1720 into securitysystem 1710 as an authorized control device. Once learned in, asdescribed with reference to FIG. 17 (and above), event manager 1722processes all events and messages detected by the combination of WSPmanager 1723 and the GE Security wireless transceiver module 1725.

In another embodiment, gateway 1720 incorporates a plurality of wirelesstransceivers 1725 and associated protocols managed by wireless protocolmanager 1726. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1711, wireless devices1713, and wired devices 1714. For example a wireless sensor from onemanufacturer may be utilized to control a device using a differentprotocol from a different manufacturer.

In another embodiment, gateway 1720 incorporates a wired interface tosecurity system 1710, and incorporates a plurality of wirelesstransceivers 1725 and associated protocols managed by wireless protocolmanager 1726. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1711, wireless devices1713, and wired devices 1714.

Of course, while an illustrative embodiment of an architecture of thesystem of an embodiment is described in detail herein with respect toFIG. 17 , one of skill in the art will understand that modifications tothis architecture may be made without departing from the scope of thedescription presented herein. For example, the functionality describedherein may be allocated differently between client and server, oramongst different server or processor-based components. Likewise, theentire functionality of the gateway 1720 described herein could beintegrated completely within an existing security system 1710. In suchan embodiment, the architecture could be directly integrated with asecurity system 1710 in a manner consistent with the currently describedembodiments.

FIG. 18 is a flow diagram for wirelessly ‘learning’ the Gateway into anexisting security system and discovering extant sensors, under anembodiment. The learning interfaces gateway 1720 with security system1710. Gateway 1720 powers up 1810 and initiates software sequences 1820and 1825 to identify accessible WSPs 1711 and wireless devices 1713,respectively (e.g., one or more WSPs and/or devices within range ofgateway 1720). Once identified, WSP 1711 is manually or automaticallyset into ‘learn mode’ 1830, and gateway 1720 utilizes availableprotocols to add 1840 itself as an authorized control device in securitysystem 1710. Upon successful completion of this task, WSP 1711 ismanually or automatically removed from ‘learn mode’ 1850.

Gateway 1720 utilizes the appropriate protocols to mimic 1860 the firstidentified device 1714. In this operation gateway 1720 identifies itselfusing the unique or pseudo-unique identifier of the first found device1714, and sends an appropriate change of state message over RF Link1770. In the event that WSP 1711 responds to this change of statemessage, the device 1714 is then added 1870 to the system in database1750. Gateway 1720 associates 1880 any other information (such as zonename or token-based identifier) with this device 1714 in database 1750,enabling gateway 1720, user interface modules, or any application toretrieve this associated information.

In the event that WSP 1711 does not respond to the change of statemessage, the device 1714 is not added 1870 to the system in database1750, and this device 1714 is identified as not being a part of securitysystem 1710 with a flag, and is either ignored or added as anindependent device, at the discretion of the system provisioning rules.Operations hereunder repeat 1885 operations 1860, 1870, 1880 for alldevices 1714 if applicable. Once all devices 1714 have been tested inthis way, the system begins operation 1890.

In another embodiment, gateway 1720 utilizes a wired connection to WSP1711, but also incorporates a wireless transceiver 1725 to communicatedirectly with devices 1714. In this embodiment, operations under 1820above are removed, and operations under 1840 above are modified so thesystem of this embodiment utilizes wireline protocols to add itself asan authorized control device in security system 1710.

A description of an example embodiment follows in which the Gateway(FIG. 17 , element 1720) is the iHub available from iControl Networks,Palo Alto, Calif., and described in detail herein. In this example thegateway is “automatically” installed with a security system.

The automatic security system installation begins with the assignment ofan authorization key to components of the security system (e.g.,gateway, kit including the gateway, etc.). The assignment of anauthorization key is done in lieu of creating a user account. Aninstaller later places the gateway in a user's premises along with thepremises security system. The installer uses a computer to navigate to aweb portal (e.g., integrated security system web interface), logs in tothe portal, and enters the authorization key of the installed gatewayinto the web portal for authentication. Once authenticated, the gatewayautomatically discovers devices at the premises (e.g., sensors, cameras,light controls, etc.) and adds the discovered devices to the system or“network”. The installer assigns names to the devices, and testsoperation of the devices back to the server (e.g., did the door open,did the camera take a picture, etc.). The security device information isoptionally pushed or otherwise propagated to a security panel and/or tothe server network database. The installer finishes the installation,and instructs the end user on how to create an account, username, andpassword. At this time the user enters the authorization key whichvalidates the account creation (uses a valid authorization key toassociate the network with the user's account). New devices maysubsequently be added to the security network in a variety of ways(e.g., user first enters a unique ID for each device/sensor and names itin the server, after which the gateway can automatically discover andconfigure the device).

A description of another example embodiment follows in which thesecurity system (FIG. 17 , element 1710) is a Dialog system and the WSP(FIG. 17 , element 1711) is a SimonXT available from General ElectricSecurity, and the Gateway (FIG. 17 , element 1720) is the iHub availablefrom iControl Networks, Palo Alto, Calif., and described in detailherein. Descriptions of the install process for the SimonXT and iHub arealso provided below.

GE Security's Dialog network is one of the most widely deployed andtested wireless security systems in the world. The physical RF networkis based on a 319.5 MHz unlicensed spectrum, with a bandwidth supportingup to 19 Kbps communications. Typical use of this bandwidth—even inconjunction with the integrated security system—is far less than that.Devices on this network can support either one-way communication (eithera transmitter or a receiver) or two-way communication (a transceiver).Certain GE Simon, Simon XT, and Concord security control panelsincorporate a two-way transceiver as a standard component. The gatewayalso incorporates the same two-way transceiver card. The physical linklayer of the network is managed by the transceiver module hardware andfirmware, while the coded payload bitstreams are made available to theapplication layer for processing.

Sensors in the Dialog network typically use a 60-bit protocol forcommunicating with the security panel transceiver, while security systemkeypads and the gateway use the encrypted 80-bit protocol. The Dialognetwork is configured for reliability, as well as low-power usage. Manydevices are supervised, i.e. they are regularly monitored by the system‘master’ (typically a GE security panel), while still maintainingexcellent power usage characteristics. A typical door window sensor hasa battery life in excess of 5-7 years.

The gateway has two modes of operation in the Dialog network: a firstmode of operation is when the gateway is configured or operates as a‘slave’ to the GE security panel; a second mode of operation is when thegateway is configured or operates as a ‘master’ to the system in theevent a security panel is not present. In both configurations, thegateway has the ability to ‘listen’ to network traffic, enabling thegateway to continually keep track of the status of all devices in thesystem. Similarly, in both situations the gateway can address andcontrol devices that support setting adjustments (such as the GEwireless thermostat).

In the configuration in which the gateway acts as a ‘slave’ to thesecurity panel, the gateway is ‘learned into’ the system as a GEwireless keypad. In this mode of operation, the gateway emulates asecurity system keypad when managing the security panel, and can querythe security panel for status and ‘listen’ to security panel events(such as alarm events).

The gateway incorporates an RF Transceiver manufactured by GE Security,but is not so limited. This transceiver implements the Dialog protocolsand handles all network message transmissions, receptions, and timing.As such, the physical, link, and protocol layers of the communicationsbetween the gateway and any GE device in the Dialog network are totallycompliant with GE Security specifications.

At the application level, the gateway emulates the behavior of a GEwireless keypad utilizing the GE Security 80-bit encrypted protocol, andonly supported protocols and network traffic are generated by thegateway. Extensions to the Dialog RF protocol of an embodiment enablefull control and configuration of the panel, and iControl can bothautomate installation and sensor enrollment as well as directconfiguration downloads for the panel under these protocol extensions.

As described above, the gateway participates in the GE Security networkat the customer premises. Because the gateway has intelligence and atwo-way transceiver, it can ‘hear’ all of the traffic on that network.The gateway makes use of the periodic sensor updates, state changes, andsupervisory signals of the network to maintain a current state of thepremises. This data is relayed to the integrated security system server(e.g., FIG. 2 , element 260) and stored in the event repository for useby other server components. This usage of the GE Security RF network iscompletely non-invasive; there is no new data traffic created to supportthis activity.

The gateway can directly (or indirectly through the Simon XT panel)control two-way devices on the network. For example, the gateway candirect a GE Security Thermostat to change its setting to ‘Cool’ from‘Off’, as well as request an update on the current temperature of theroom. The gateway performs these functions using the existing GE Dialogprotocols, with little to no impact on the network; a gateway devicecontrol or data request takes only a few dozen bytes of data in anetwork that can support 19 Kbps.

By enrolling with the Simon XT as a wireless keypad, as describedherein, the gateway includes data or information of all alarm events, aswell as state changes relevant to the security panel. This informationis transferred to the gateway as encrypted packets in the same way thatthe information is transferred to all other wireless keypads on thenetwork.

Because of its status as an authorized keypad, the gateway can alsoinitiate the same panel commands that a keypad can initiate. Forexample, the gateway can arm or disarm the panel using the standardDialog protocol for this activity. Other than the monitoring of standardalarm events like other network keypads, the only incremental datatraffic on the network as a result of the gateway is the infrequentremote arm/disarm events that the gateway initiates, or infrequentqueries on the state of the panel.

The gateway is enrolled into the Simon XT panel as a ‘slave’ devicewhich, in an embodiment, is a wireless keypad. This enables the gatewayfor all necessary functionality for operating the Simon XT systemremotely, as well as combining the actions and information ofnon-security devices such as lighting or door locks with GE Securitydevices. The only resource taken up by the gateway in this scenario isone wireless zone (sensor ID).

The gateway of an embodiment supports three forms of sensor and panelenrollment/installation into the integrated security system, but is notlimited to this number of enrollment/installation options. Theenrollment/installation options of an embodiment include installerinstallation, kitting, and panel, each of which is described below.

Under the installer option, the installer enters the sensor IDs at timeof installation into the integrated security system web portal oriScreen. This technique is supported in all configurations andinstallations.

Kits can be pre-provisioned using integrated security systemprovisioning applications when using the kitting option. At kittingtime, multiple sensors are automatically associated with an account, andat install time there is no additional work required.

In the case where a panel is installed with sensors already enrolled(i.e. using the GE Simon XT enrollment process), the gateway has thecapability to automatically extract the sensor information from thesystem and incorporate it into the user account on the integratedsecurity system server.

The gateway and integrated security system of an embodiment uses anauto-learn process for sensor and panel enrollment in an embodiment. Thedeployment approach of an embodiment can use additional interfaces thatGE Security is adding to the Simon XT panel. With these interfaces, thegateway has the capability to remotely enroll sensors in the panelautomatically. The interfaces include, but are not limited to, thefollowing: EnrollDevice(ID, type, name, zone, group);SetDeviceParameters(ID, type, Name, zone, group),GetDeviceParameters(zone); and RemoveDevice(zone).

The integrated security system incorporates these new interfaces intothe system, providing the following install process. The install processcan include integrated security system logistics to handle kitting andpre-provisioning. Pre-kitting and logistics can include apre-provisioning kitting tool provided by integrated security systemthat enables a security system vendor or provider (“provider”) to offerpre-packaged initial ‘kits’. This is not required but is recommended forsimplifying the install process. This example assumes a ‘Basic’ kit ispreassembled and includes one (1) Simon XT, three (3) Door/windowsensors, one (1) motion sensor, one (1) gateway, one (1) keyfob, two (2)cameras, and ethernet cables. The kit also includes a sticker page withall Zones (1-24) and Names (full name list).

The provider uses the integrated security system kitting tool toassemble ‘Basic’ kit packages. The contents of different types ofstarter kits may be defined by the provider. At the distributionwarehouse, a worker uses a bar code scanner to scan each sensor and thegateway as it is packed into the box. An ID label is created that isattached to the box. The scanning process automatically associates allthe devices with one kit, and the new ID label is the unique identifierof the kit. These boxes are then sent to the provider for distributionto installer warehouses. Individual sensors, cameras, etc. are also sentto the provider installer warehouse. Each is labeled with its ownbarcode/ID.

An installation and enrollment procedure of a security system includinga gateway is described below as one example of the installation process.

-   1. Order and Physical Install Process    -   a. Once an order is generated in the iControl system, an account        is created and an install ticket is created and sent        electronically to the provider for assignment to an installer.    -   b. The assigned installer picks up his/her ticket(s) and fills        his/her truck with Basic and/or Advanced starter kits. He/she        also keeps a stock of individual sensors, cameras, iHubs, Simon        XTs, etc. Optionally, the installer can also stock homeplug        adapters for problematic installations.    -   c. The installer arrives at the address on the ticket, and pulls        out the Basic kit. The installer determines sensor locations        from a tour of the premises and discussion with the homeowner.        At this point assume the homeowner requests additional equipment        including an extra camera, two (2) additional door/window        sensors, one (1) glass break detector, and one (1) smoke        detector.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home as directed by the homeowner, and routes the phone line        to Simon XT if available. GPRS and Phone numbers pre-programmed        in SimonXT to point to the provider Central Monitoring Station        (CMS).    -   e. Installer places gateway in the home in the vicinity of a        router and cable modem. Installer installs an ethernet line from        gateway to router and plugs gateway into an electrical outlet.-   2. Associate and Enroll gateway into SimonXT    -   a. Installer uses either his/her own laptop plugged into router,        or homeowners computer to go to the integrated security system        web interface and log in with installer ID/pass.    -   b. Installer enters ticket number into admin interface, and        clicks ‘New Install’ button. Screen prompts installer for kit ID        (on box's barcode label).    -   c. Installer clicks ‘Add SimonXT’. Instructions prompt installer        to put Simon XT into install mode, and add gateway as a wireless        keypad. It is noted that this step is for security only and can        be automated in an embodiment.    -   d. Installer enters the installer code into the Simon XT.        Installer Learns ‘gateway’ into the panel as a wireless keypad        as a group 1 device.    -   e. Installer goes back to Web portal, and clicks the ‘Finished        Adding SimonXT’ button.-   3. Enroll Sensors into SimonXT via iControl    -   a. All devices in the Basic kit are already associated with the        user's account.    -   b. For additional devices, Installer clicks ‘Add Device’ and        adds the additional camera to the user's account (by typing in        the camera ID/Serial #).    -   c. Installer clicks ‘Add Device’ and adds other sensors (two (2)        door/window sensors, one (1) glass break sensor, and one (1)        smoke sensor) to the account (e.g., by typing in IDs).    -   d. As part of Add Device, Installer assigns zone, name, and        group to the sensor. Installer puts appropriate Zone and Name        sticker on the sensor temporarily.    -   e. All sensor information for the account is pushed or otherwise        propagated to the iConnect server, and is available to propagate        to CMS automation software through the CMS application        programming interface (API).    -   f. Web interface displays ‘Installing Sensors in System . . . ’        and automatically adds all of the sensors to the Simon XT panel        through the GE RF link.    -   g. Web interface displays ‘Done Installing’→all sensors show        green.-   4. Place and Tests Sensors in Home    -   a. Installer physically mounts each sensor in its desired        location, and removes the stickers.    -   b. Installer physically mounts WiFi cameras in their location        and plugs into AC power. Optional fishing of low voltage wire        through wall to remove dangling wires. Camera transformer is        still plugged into outlet but wire is now inside the wall.    -   c. Installer goes to Web interface and is prompted for automatic        camera install. Each camera is provisioned as a private,        encrypted Wifi device on the gateway secured sandbox network,        and firewall NAT traversal is initiated. Upon completion the        customer is prompted to test the security system.    -   d. Installer selects the ‘Test System’ button on the web        portal—the SimonXT is put into Test mode by the gateway over GE        RF.    -   e. Installer manually tests the operation of each sensor,        receiving an audible confirmation from SimonXT.    -   f. gateway sends test data directly to CMS over broadband link,        as well as storing the test data in the user's account for        subsequent report generation.    -   g. Installer exits test mode from the Web portal.-   5. Installer instructs customer on use of the Simon XT, and shows    customer how to log into the iControl web and mobile portals.    Customer creates a username/password at this time.-   6. Installer instructs customer how to change Simon XT user code    from the Web interface. Customer changes user code which is pushed    to SimonXT automatically over GE RF.

An installation and enrollment procedure of a security system includinga gateway is described below as an alternative example of theinstallation process. This installation process is for use for enrollingsensors into the SimonXT and integrated security system and iscompatible with all existing GE Simon panels.

The integrated security system supports all pre-kitting functionalitydescribed in the installation process above. However, for the purpose ofthe following example, no kitting is used.

-   -   1. Order and Physical Install Process        -   a. Once an order is generated in the iControl system, an            account is created and an install ticket is created and sent            electronically to the security system provider for            assignment to an installer.        -   b. The assigned installer picks up his/her ticket(s) and            fills his/her truck with individual sensors, cameras, iHubs,            Simon XTs, etc. Optionally, the installer can also stock            homeplug adapters for problematic installations.        -   c. The installer arrives at the address on the ticket, and            analyzes the house and talks with the homeowner to determine            sensor locations. At this point assume the homeowner            requests three (3) cameras, five (5) door/window sensors,            one (1) glass break detector, one (1) smoke detector, and            one (1) keyfob.        -   d. Installer mounts SimonXT in the kitchen or other location            in the home. The installer routes a phone line to Simon XT            if available. GPRS and Phone numbers are pre-programmed in            SimonXT to point to the provider CMS.        -   e. Installer places gateway in home in the vicinity of a            router and cable modem, and installs an ethernet line from            gateway to the router, and plugs gateway into an electrical            outlet.    -   2. Associate and Enroll gateway into SimonXT        -   a. Installer uses either his/her own laptop plugged into            router, or homeowners computer to go to the integrated            security system web interface and log in with an installer            ID/pass.        -   b. Installer enters ticket number into admin interface, and            clicks ‘New Install’ button. Screen prompts installer to add            devices.        -   c. Installer types in ID of gateway, and it is associated            with the user's account.        -   d. Installer clicks ‘Add Device’ and adds the cameras to the            user's account (by typing in the camera ID/Serial #).        -   e. Installer clicks ‘Add SimonXT’. Instructions prompt            installer to put Simon XT into install mode, and add gateway            as a wireless keypad.        -   f. Installer goes to Simon XT and enters the installer code            into the Simon XT. Learns ‘gateway’ into the panel as a            wireless keypad as group 1 type sensor.        -   g. Installer returns to Web portal, and clicks the ‘Finished            Adding SimonXT’ button.        -   h. Gateway now is alerted to all subsequent installs over            the security system RF.    -   3. Enroll Sensors into SimonXT via iControl        -   a. Installer clicks ‘Add Simon XT Sensors’—Displays            instructions for adding sensors to Simon XT.        -   b. Installer goes to Simon XT and uses Simon XT install            process to add each sensor, assigning zone, name, group.            These assignments are recorded for later use.        -   c. The gateway automatically detects each sensor addition            and adds the new sensor to the integrated security system.        -   d. Installer exits install mode on the Simon XT, and returns            to the Web portal.        -   e. Installer clicks ‘Done Adding Devices’.        -   f. Installer enters zone/sensor naming from recorded notes            into integrated security system to associate sensors to            friendly names.        -   g. All sensor information for the account is pushed to the            iConnect server, and is available to propagate to CMS            automation software through the CMS API.    -   4. Place and Tests Sensors in Home        -   a. Installer physically mounts each sensor in its desired            location.        -   b. Installer physically mounts Wifi cameras in their            location and plugs into AC power. Optional fishing of low            voltage wire through wall to remove dangling wires. Camera            transformer is still plugged into outlet but wire is now            inside the wall.        -   c. Installer puts SimonXT into Test mode from the keypad.        -   d. Installer manually tests the operation of each sensor,            receiving an audible confirmation from SimonXT.        -   e. Installer exits test mode from the Simon XT keypad.        -   f. Installer returns to web interface and is prompted to            automatically set up cameras. After waiting for completion            cameras are now provisioned and operational.    -   5. Installer instructs customer on use of the Simon XT, and        shows customer how to log into the integrated security system        web and mobile portals. Customer creates a username/password at        this time.    -   6. Customer and Installer observe that all sensors/cameras are        green.    -   7. Installer instructs customer how to change Simon XT user code        from the keypad. Customer changes user code and stores in        SimonXT.    -   8. The first time the customer uses the web portal to Arm/Disarm        system the web interface prompts the customer for the user code,        which is then stored securely on the server. In the event the        user code is changed on the panel the web interface once again        prompts the customer.

The panel of an embodiment can be programmed remotely. The CMS pushesnew programming to SimonXT over a telephone or GPRS link. Optionally,iControl and GE provide a broadband link or coupling to the gateway andthen a link from the gateway to the Simon XT over GE RF.

Embodiments described herein include a device comprising a housing at apremise. The housing contains a touchscreen display coupled to aprocessor. The processor is coupled to at least one remote network. Thedevice of an embodiment includes an application engine coupled to theprocessor. The application engine controls a plurality of applicationsexecuting under the processor. The device of an embodiment includes areceptacle in the housing. The receptacle includes a connector coupledto the processor. The device of an embodiment includes a plurality ofmodules each having a form-factor for connecting to the receptacle. Eachmodule of the plurality of modules includes components corresponding toa function of a plurality of functions. The components of each moduleare coupled to the processor and the application engine via theconnection of the module to the receptacle and the componentsdynamically reconfigure the touchscreen to operate according to thefunction of the module.

Embodiments described herein include a device comprising: a housing at apremise, wherein the housing contains a touchscreen display coupled to aprocessor, wherein the processor is coupled to at least one remotenetwork; an application engine coupled to the processor, wherein theapplication engine controls a plurality of applications executing underthe processor; a receptacle in the housing, wherein the receptacleincludes a connector coupled to the processor; and a plurality ofmodules each having a form-factor for connecting to the receptacle,wherein each module of the plurality of modules includes componentscorresponding to a function of a plurality of functions, wherein thecomponents of each module are coupled to the processor and theapplication engine via the connection of the module to the receptacleand the components dynamically reconfigure the touchscreen to operateaccording to the function of the module.

The plurality of modules of an embodiment includes an energy managementmodule for energy management on the premise.

The plurality of modules of an embodiment includes a thermostat modulefor temperature management on the premise.

The plurality of modules of an embodiment includes a remote healthmonitoring module for human health monitoring on the premise.

The plurality of modules of an embodiment includes a monitoring modulefor human monitoring on the premise.

A plurality of interfaces of an embodiment coupled to the processor andpresented to a user via the touchscreen, wherein the plurality ofinterfaces correspond to the plurality of modules.

An interface of the plurality of interfaces of an embodiment correspondsto the function of the module.

The device of an embodiment comprises modular applications that presentthe plurality of interfaces on the touchscreen.

The modular applications of an embodiment are downloaded via the atleast one remote network.

The processor of an embodiment dynamically updates the plurality ofinterfaces using the modular applications.

The plurality of interfaces of an embodiment provides interactivity witha plurality of devices located at the premise.

A device of the plurality of devices of an embodiment is a radiofrequency (RF) device.

A device of the plurality of devices of an embodiment is a Z-Wavedevice.

A device of the plurality of devices of an embodiment is an InternetProtocol device.

A device of the plurality of devices of an embodiment is a camera.

A device of the plurality of devices of an embodiment is anothertouchscreen.

A device of the plurality of devices of an embodiment is a devicecontroller that controls an attached device.

The device controller of an embodiment is a thermostat.

The device controller of an embodiment is an energy meter.

A device of the plurality of devices of an embodiment is a sensor.

The plurality of modules of an embodiment includes a security modulethat generates through the touchscreen a security network by integratinginto the touchscreen a security system located at the premise, whereinthe security system includes a plurality of security components.

The security module of an embodiment includes security system softwarethat runs on the processor of the touchscreen, wherein the securitysystem software controls operation of the security system andinteroperability of the plurality of security components.

The security system software of an embodiment controls processing ofstate data of the plurality of security components.

The security system software of an embodiment determines alarm systemstate.

The security system software of an embodiment generates alarm reports.

The touchscreen with the security module of an embodiment establishescommunication with the at least one remote network.

The touchscreen with the security module of an embodiment generates asubnetwork in the premise which incorporates the touchscreen, whereinthe subnetwork includes at least one component and is independent fromthe security network.

The touchscreen of an embodiment controls an exchange of data between afirst component of the security network and a second component of one ofthe subnetwork and the remote network.

The device of an embodiment comprises a security interface and a networkinterface coupled to the processor and presented to a user via thetouchscreen, wherein the security interface provides the user withcontrol of functions of the security system and access to data collectedby the security system, wherein the network interface allows the user totransfer content to and from the at least one remote network.

The device of an embodiment comprises a first application engine coupledto the processor, wherein the first application engine executes asecurity application that provides the security interface.

The device of an embodiment comprises a second application enginecoupled to the processor, wherein the second application engine executesa content application that provides the network interface.

The touchscreen with a module of an embodiment generates a subnetwork inthe premise which incorporates the touchscreen, wherein the subnetworkincludes at least one component and is independent from any othernetwork of the premise.

The touchscreen of an embodiment controls an exchange of data betweenthe at least one component of the subnetwork and any other component ofthe premise coupled to the touchscreen.

The device of an embodiment comprises a remote server coupled to thetouchscreen, the remote server managing at least one of the touchscreenand the plurality of functions.

The remote server of an embodiment allows a user to configure content ofthe touchscreen.

The remote server of an embodiment provides user portals that enablecontent and information displayed on the touchscreen to be displayed onremote devices.

The remote devices of an embodiment access the plurality of functionsvia the portals.

The touchscreen of an embodiment includes a wireless transceiver forcommunicating with remote devices.

At least one module of an embodiment includes a wireless transceiver forcommunicating with remote devices.

The touchscreen of an embodiment plays live video from a camera at thepremise.

The device of an embodiment comprises a network interface coupled to theprocessor and presented to a user via the touchscreen, wherein thenetwork interface allows the user to transfer content to and from the atleast one remote network.

The network interface of an embodiment allows the user to integrate thecontent with the plurality of applications.

The network interface of an embodiment allows the user to integrate thecontent with components of the modules.

The content of an embodiment includes interactive content in the form ofinternet widgets.

The content of an embodiment includes at least one of an application, anupdate to an application of the plurality of applications, and an updateto a component of a module.

The network interface of an embodiment allows the user to controlfunctions of devices of the premise.

The plurality of applications of an embodiment provides interactivitywith the plurality of functions.

The plurality of applications of an embodiment provides interactivitywith a plurality of devices of the premise.

The plurality of devices of an embodiment is coupled to the processor.

The plurality of devices of an embodiment is coupled to the processorvia a wireless coupling.

The plurality of devices of an embodiment is coupled to the processorvia a module of the plurality of modules.

The plurality of applications of an embodiment includes a residentapplication that manages interactions between the plurality ofapplications.

The resident application of an embodiment determines a priority of eachapplication of the plurality of applications and manages the pluralityof applications according to the priority.

The resident application of an embodiment allows a first applicationhaving a first priority to override a second application having a secondpriority when the first priority is higher than the second priority.

The resident application of an embodiment manages interactions between aplurality of devices at the premise.

The device of an embodiment comprises a core engine coupled to theprocessor, the core engine controlling dynamic provisioning of theplurality of applications and content.

The core engine of an embodiment manages images received from aplurality devices of the premise.

The images of an embodiment include video.

The processor of an embodiment is coupled to the at least one remotenetwork via a broadband coupling.

The processor of an embodiment is coupled to the at least one remotenetwork via a cellular data coupling.

Embodiments described herein include a method comprising containing in ahousing at a premise a touchscreen display coupled to a processor. Thehousing comprises a receptacle that includes a connector coupled to theprocessor. The method of an embodiment comprises coupling the processorto at least one remote network. The method of an embodiment comprisescontrolling a plurality of applications executing under the processorwith an application engine. The method of an embodiment comprisesreceiving at the receptacle individual ones of a plurality of modules.Each module of the plurality of modules includes componentscorresponding to a function of a plurality of functions. The componentsof each module are coupled to the processor and the application enginevia the connection of the module to the receptacle and the componentsdynamically reconfigure the touchscreen to operate according to thefunction of the module.

Embodiments described herein include a method comprising: containing ina housing at a premise a touchscreen display coupled to a processor,wherein the housing comprises a receptacle that includes a connectorcoupled to the processor; coupling the processor to at least one remotenetwork; controlling a plurality of applications executing under theprocessor with an application engine; and receiving at the receptacleindividual ones of a plurality of modules, wherein each module of theplurality of modules includes components corresponding to a function ofa plurality of functions, wherein the components of each module arecoupled to the processor and the application engine via the connectionof the module to the receptacle and the components dynamicallyreconfigure the touchscreen to operate according to the function of themodule.

The plurality of modules of an embodiment includes at least one of anenergy management module for energy management on the premise, athermostat module for temperature management on the premise, a remotehealth monitoring module for human health monitoring on the premise, anda monitoring module for human monitoring on the premise.

The method of an embodiment comprises presenting a plurality ofinterfaces to a user via the touchscreen, wherein the plurality ofinterfaces are coupled to the processor and correspond to the pluralityof modules.

An interface of the plurality of interfaces of an embodiment correspondsto the function of the module.

The method of an embodiment comprises modular applications that presentthe plurality of interfaces on the touchscreen, wherein the modularapplications are downloaded via the at least one remote network, whereinthe processor dynamically updates the plurality of interfaces using themodular applications.

The plurality of interfaces of an embodiment provides interactivity witha plurality of devices located at the premise.

A device of the plurality of devices of an embodiment is a radiofrequency (RF) device.

The plurality of devices of an embodiment includes at least one of aZ-Wave device, an Internet Protocol device, a camera, anothertouchscreen, a device controller that controls an attached device, and asensor.

The plurality of modules of an embodiment includes a security modulethat generates through the touchscreen a security network by integratinginto the touchscreen a security system located at the premise, whereinthe security system includes a plurality of security components.

The security module of an embodiment includes security system softwarethat runs on the processor of the touchscreen, wherein the securitysystem software controls operation of the security system andinteroperability of the plurality of security components.

The method of an embodiment comprises controlling with the securitysystem software processing of state data of the plurality of securitycomponents.

The method of an embodiment comprises determining via the securitysystem software alarm system state and generating alarm reports.

The method of an embodiment comprises using the touchscreen with thesecurity module to generate a subnetwork in the premise whichincorporates the touchscreen, wherein the subnetwork includes at leastone component and is independent from the security network.

The method of an embodiment comprises controlling via the touchscreen anexchange of data between a first component of the security network and asecond component of one of the subnetwork and the remote network.

The method of an embodiment comprises generating and presenting to auser via the touchscreen a security interface and a network interface,wherein the security interface provides the user with control offunctions of the security system and access to data collected by thesecurity system, wherein the network interface allows the user totransfer content to and from the at least one remote network.

The method of an embodiment comprises running a first application engineunder the processor, wherein the first application engine executes asecurity application that provides the security interface.

The method of an embodiment comprises running a second applicationengine under the processor, wherein the second application engineexecutes a content application that provides the network interface.

The method of an embodiment comprises generating via the touchscreen anda module a subnetwork in the premise which incorporates the touchscreen,wherein the subnetwork includes at least one component and isindependent from any other network of the premise.

The method of an embodiment comprises controlling via the touchscreen anexchange of data between the at least one component of the subnetworkand any other component of the premise coupled to the touchscreen.

The method of an embodiment comprises establishing a coupling between aremote server and the touchscreen, the remote server managing at leastone of the touchscreen and the plurality of functions.

The method of an embodiment comprises accessing the plurality offunctions via remote devices.

The touchscreen of an embodiment includes a wireless transceiver forcommunicating with remote devices.

At least one module of an embodiment includes a wireless transceiver forcommunicating with remote devices.

The method of an embodiment comprises presenting a network interface toa user via the touchscreen, transferring content to and from the atleast one remote network using the network interface.

The network interface of an embodiment allows the user to integrate thecontent with the plurality of applications.

The network interface of an embodiment allows the user to integrate thecontent with components of the modules.

The content of an embodiment includes at least one of interactivecontent in the form of internet widgets, an application, an update to anapplication of the plurality of applications, and an update to acomponent of a module.

The plurality of applications of an embodiment provides interactivitywith the plurality of functions.

The plurality of applications of an embodiment provides interactivitywith a plurality of devices of the premise.

The plurality of devices of an embodiment is coupled to the processor.

The plurality of devices of an embodiment is coupled to the processorvia a wireless coupling.

The plurality of devices of an embodiment is coupled to the processorvia a module of the plurality of modules.

The plurality of applications of an embodiment includes a residentapplication that manages interactions between the plurality ofapplications.

The resident application of an embodiment determines a priority of eachapplication of the plurality of applications and manages the pluralityof applications according to the priority.

The resident application of an embodiment allows a first applicationhaving a first priority to override a second application having a secondpriority when the first priority is higher than the second priority.

The resident application of an embodiment manages interactions between aplurality of devices at the premise.

The method of an embodiment comprises a core engine coupled to theprocessor, the core engine controlling dynamic provisioning of theplurality of applications and content.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof.

The touchscreen platform can be a component of a single system, multiplesystems, and/or geographically separate systems. The touchscreenplatform can also be a subcomponent or subsystem of a single system,multiple systems, and/or geographically separate systems. Thetouchscreen platform can be coupled to one or more other components (notshown) of a host system or a system coupled to the host system.

One or more components of the touchscreen platform and/or acorresponding system or application to which the touchscreen platform iscoupled or connected includes and/or runs under and/or in associationwith a processing system. The processing system includes any collectionof processor-based devices or computing devices operating together, orcomponents of processing systems or devices, as is known in the art. Forexample, the processing system can include one or more of a portablecomputer, portable communication device operating in a communicationnetwork, and/or a network server. The portable computer can be any of anumber and/or combination of devices selected from among personalcomputers, personal digital assistants, portable computing devices, andportable communication devices, but is not so limited. The processingsystem can include components within a larger computer system.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the touchscreen platform canbe located together or in separate locations. Communication paths couplethe components and include any medium for communicating or transferringfiles among the components. The communication paths include wirelessconnections, wired connections, and hybrid wireless/wired connections.The communication paths also include couplings or connections tonetworks including local area networks (LANs), metropolitan areanetworks (MANs), wide area networks (WANs), proprietary networks,interoffice or backend networks, and the Internet. Furthermore, thecommunication paths include removable fixed mediums like floppy disks,hard disk drives, and CD-ROM disks, as well as flash RAM, UniversalSerial Bus (USB) connections, RS-232 connections, telephone lines,buses, and electronic mail messages.

Aspects of the touchscreen platform and corresponding systems andmethods described herein may be implemented as functionality programmedinto any of a variety of circuitry, including programmable logic devices(PLDs), such as field programmable gate arrays (FPGAs), programmablearray logic (PAL) devices, electrically programmable logic and memorydevices and standard cell-based devices, as well as application specificintegrated circuits (ASICs). Some other possibilities for implementingaspects of the touchscreen platform and corresponding systems andmethods include: microcontrollers with memory (such as electronicallyerasable programmable read only memory (EEPROM)), embeddedmicroprocessors, firmware, software, etc. Furthermore, aspects of thetouchscreen platform and corresponding systems and methods may beembodied in microprocessors having software-based circuit emulation,discrete logic (sequential and combinatorial), custom devices, fuzzy(neural) logic, quantum devices, and hybrids of any of the above devicetypes. Of course the underlying device technologies may be provided in avariety of component types, e.g., metal-oxide semiconductor field-effecttransistor (MOSFET) technologies like complementary metal-oxidesemiconductor (CMOS), bipolar technologies like emitter-coupled logic(ECL), polymer technologies (e.g., silicon-conjugated polymer andmetal-conjugated polymer-metal structures), mixed analog and digital,etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the touchscreen platform andcorresponding systems and methods is not intended to be exhaustive or tolimit the systems and methods to the precise forms disclosed. Whilespecific embodiments of, and examples for, the touchscreen platform andcorresponding systems and methods are described herein for illustrativepurposes, various equivalent modifications are possible within the scopeof the systems and methods, as those skilled in the relevant art willrecognize. The teachings of the touchscreen platform and correspondingsystems and methods provided herein can be applied to other systems andmethods, not only for the systems and methods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the touchscreen platform and corresponding systems and methodsin light of the above detailed description.

What is claimed is:
 1. An apparatus comprising: an interface devicecomprising: a housing comprising one or more processors; a display incommunication with the one or more processors; a network interfaceconfigured to enable communication, via a first network located at apremises, between the interface device and a security system located atthe premises; and a module connector in communication with the one ormore processors, wherein the module connector is configured as aphysical connection interface for the interface device; and a modulecomprising computer readable instructions and configured to removablyand physically couple with the module connector, wherein the module,when coupled to the module connector and based on the computer readableinstructions, configures the interface device to establish a secondnetwork, located at the premises, different from the first network, andcontrol communication, via at least the second network and usingfirmware, of data between the security system and a computing devicelocated at the premises, in communication with the second network, anddifferent from the interface device, wherein the module is one of aplurality of modules configured to separately couple with the moduleconnector and each of the plurality of modules enables a differentfunctionality.
 2. The apparatus of claim 1, wherein the security systemcomprises one or more of an alarm system controller, a sensor, or acamera.
 3. The apparatus of claim 1, wherein the computing devicecomprises one or more of an automation device, a home health device, oran energy management device.
 4. The apparatus of claim 1, wherein thesecond network comprises a subnetwork established by the interfacedevice.
 5. The apparatus of claim 1, wherein the module is configured tocontrol the computing device.
 6. The apparatus of claim 1, wherein themodule has a shape that at least partially conforms to a shape of anopening of the housing, wherein the module connector is disposed in theopening.
 7. The apparatus of claim 1, wherein the module comprises acommunication element configured to communicate with the computingdevice.
 8. The apparatus of claim 1, wherein the housing of theinterface device at least partially comprises the display and thenetwork interface, and wherein the module connector extends from areceptacle of the housing of the interface device.
 9. The apparatus ofclaim 1, wherein the module comprises one or more components thatconfigure the one or more processors to operate according to anyfunction provided by the module.
 10. The apparatus of claim 1, whereinthe computer readable instructions configure the processor of theinterface device to establish the second network.
 11. The apparatus ofclaim 1, wherein the module comprises a wireless transceiver.
 12. Theapparatus of claim 1, wherein the computer readable instructionscomprises one or more of the firmware or software stored by the module.13. A method comprising: establishing, via a first network located at apremises, communication between an interface device and a securitysystem located at the premises; determining a connection of a module tothe interface device, wherein the module comprises computer readableinstructions and is configured to removably and physically couple to theinterface device, and wherein connection of the module to the interfacedevice establishes, based on the computer readable instructions, asecond network different than the first network and located at thepremises, and wherein the module is one of a plurality of modulesconfigured to separately couple with a module connector of the interfacedevice and each of the plurality of modules enables a differentfunctionality; and controlling, based on the module configuring theinterface device with control functionality, communication, via at leastthe second network and using firmware, of data between the securitysystem and a computing device located at the premises and different fromthe interface device.
 14. The method of claim 13, wherein the securitysystem comprises one or more of an alarm system controller, a sensor, ora camera.
 15. The method of claim 13, wherein the computing devicecomprises one or more of an automation device, a home health device, oran energy management device.
 16. The method of claim 13, wherein thesecond network comprises a subnetwork established by the interfacedevice.
 17. The method of claim 13, further comprising controlling, bythe interface device and via the module, the computing device.
 18. Themethod of claim 13, wherein the module has a shape that at leastpartially conforms to a shape of an opening of a housing of theinterface device, wherein the module is configured to connect to theinterface device via a module connector disposed in the opening.
 19. Themethod of claim 13, wherein the module comprises a communication elementconfigured to communicate with the computing device.
 20. An apparatuscomprising: a housing comprising one or more processors; a display incommunication with the one or more processors; a network interfaceconfigured to enable communication, via a first network located at apremises, with a security system located at the premises; and a moduleconnector in communication with the one or more processors, wherein themodule connector is configured to removably and physically couple withone or more of a plurality of modules, wherein the plurality of modulescomprise a first module that, when coupled to the module connector andbased on computer readable instructions stored in the first module,configures the apparatus to establish a second network located at thepremises and different from the first network, and controlcommunication, via at least the second network and using firmware, ofdata between the security system and a computing device, incommunication with the second network, located at the premises.
 21. Theapparatus of claim 20, wherein the security system comprises one or moreof an alarm system controller, a sensor, or a camera.
 22. The apparatusof claim 20, wherein the computing device comprises one or more of anautomation device, a home health device, or an energy management device.23. The apparatus of claim 20, wherein the second network comprises asubnetwork established by the apparatus.
 24. The apparatus of claim 20,wherein the first module is configured to control the computing device.25. The apparatus of claim 20, wherein the first module has a shape thatat least partially conforms to a shape of an opening in the housing, andwherein the module connector is disposed in the opening of the housing.